Notes on quiet interfaces
A year of removing things instead of adding them, and what it taught me about restraint.
I spent last year on a team whose only mandate was to take things out. No new features, no new surfaces. Just: find what is loud, and make it quiet.
It was the most useful year of work I have done, and almost none of it was visible.
Loudness is not the same as size
The loudest thing on a page is rarely the biggest. It is the thing that moves when nothing else does, or the one element wearing a colour no other element wears. A single red dot outranks a headline. A tooltip that opens on hover outranks the paragraph it covers.
Once you start counting attention rather than pixels, the priorities on most screens turn out to be accidental. Nobody decided that the notification badge should be the first thing you see. It just was the last thing anyone added.
Removing is a design act
There is a persistent idea that deleting is the easy half of the job. It is not. Deciding what a screen is for is the entire job, and every deletion is that decision made out loud, with consequences.
- We removed a chart nobody could explain. Support tickets about it went to zero, which we could have guessed, and tickets about the number underneath it went to zero too, which we could not.
- We removed three of five empty states and replaced them with one honest sentence. Completion of the flow went up.
- We removed an onboarding tour. Nothing happened at all, which is its own kind of finding.
Quiet is not cold
The failure mode of restraint is a product that feels like a spreadsheet with better margins. Quiet interfaces still need warmth; they just spend it carefully. One good sentence in an empty state. A confirmation that names what you did instead of saying Success. The small pleasure of a list that scrolls exactly as fast as you expect.
You get one or two moments of personality per screen. Spend them on the parts people touch.